NO-JIRA: add TLS scan jobs for HCO - #82659
Conversation
|
@nunnatsa: This pull request explicitly references no jira issue. DetailsIn response to this: Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: nunnatsa The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
Note Reviews pausedIt looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the Use the following commands to manage reviews:
Use the checkboxes below for quick actions:
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository YAML (base), Central YAML (inherited) Review profile: CHILL Plan: Enterprise Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (1)
🚧 Files skipped from review as they are similar to previous changes (1)
WalkthroughAdds the ChangesHCO TLS scanning
Estimated code review effort: 2 (Simple) | ~10 minutes Suggested labels: Suggested reviewers: Important Pre-merge checks failedPlease resolve all errors before merging. Addressing warnings is optional. ❌ Failed checks (1 error)
✅ Passed checks (14 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
|
/pj-rehearse pull-ci-kubevirt-hyperconverged-cluster-operator-main-hco-tls-scan-aws pull-ci-kubevirt-hyperconverged-cluster-operator-main-hco-tls-scan-azure |
|
@nunnatsa: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
|
/pj-rehearse pull-ci-kubevirt-hyperconverged-cluster-operator-main-hco-tls-scan-azure |
|
@nunnatsa: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
|
/pj-rehearse pull-ci-kubevirt-hyperconverged-cluster-operator-main-hco-tls-scan-aws pull-ci-kubevirt-hyperconverged-cluster-operator-main-hco-tls-scan-azure |
|
@nunnatsa: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
|
Note GitHub couldn't provide a complete incremental comparison for this pull request, so CodeRabbit is performing a full review instead. This review may take a little longer. |
|
/pj-rehearse pull-ci-kubevirt-hyperconverged-cluster-operator-main-hco-tls-scan-aws pull-ci-kubevirt-hyperconverged-cluster-operator-main-hco-tls-scan-azure |
|
@nunnatsa: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
|
/pj-rehearse ack |
|
@nunnatsa: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
| SCAN_NAMESPACE: kubevirt-hyperconverged | ||
| SCANNER_CPU: "2" | ||
| SPOT_INSTANCES: "true" | ||
| test: |
There was a problem hiding this comment.
why there is no - ref: tls-13 step on the aws job?
|
Note GitHub couldn't provide a complete incremental comparison for this pull request, so CodeRabbit is performing a full review instead. This review may take a little longer. |
|
/pj-rehearse pull-ci-kubevirt-hyperconverged-cluster-operator-main-hco-tls-scan-aws pull-ci-kubevirt-hyperconverged-cluster-operator-main-hco-tls-scan-azure |
|
@nunnatsa: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
|
/pj-rehearse pull-ci-kubevirt-hyperconverged-cluster-operator-main-hco-tls-scan-aws pull-ci-kubevirt-hyperconverged-cluster-operator-main-hco-tls-scan-azure |
|
@nunnatsa: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
|
@nunnatsa: The following tests failed, say
Full PR test history. Your PR dashboard. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
Signed-off-by: Nahshon Unna Tsameret <nunnatsa@redhat.com>
|
Note GitHub couldn't provide a complete incremental comparison for this pull request, so CodeRabbit is performing a full review instead. This review may take a little longer. |
|
/pj-rehearse pull-ci-kubevirt-hyperconverged-cluster-operator-main-hco-tls-scan-aws pull-ci-kubevirt-hyperconverged-cluster-operator-main-hco-tls-scan-azure |
|
@nunnatsa: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
|
[REHEARSALNOTIFIER]
Interacting with pj-rehearseComment: Once you are satisfied with the results of the rehearsals, comment: |
Summary by CodeRabbit
Adds optional AWS and Azure TLS scan jobs to the HCO OpenShift CI configuration. Both jobs install HCO, run
tls-scanner-run, and runtls-13. The AWS job uses spot instances and enables KVM emulation.